build: use full installer IDE for local dev (ZIP stays CI-only); bump 262 → 2026.2.1 - #960
Merged
Conversation
The multi-OS ZIP distribution is an incomplete runtime: it omits the JBR and native components (JCEF, platform-daemon), which breaks runIde on 2026+ builds locally. Keep the ZIP on CI, where it enables the OS-agnostic shared IDE cache and only headless tests run, but resolve the OS-specific installer locally so runIde has a complete, launchable IDE. Gate on the CI environment variable (always "true" on GitHub Actions) via the existing isCI flag, and log the chosen artifact so the selection is visible in build output rather than silent. Assisted-by: Claude:claude-opus-4-8
There was a problem hiding this comment.
Pull request overview
Updates the Gradle build to choose the appropriate IntelliJ Platform IDE distribution per environment (ZIP on CI for shared caching; OS installer locally for a runnable runIde on 2026+), and bumps the 262 IDE target to 2026.2.1.
Changes:
- Select IDE artifact via
useInstaller = !isCIfor both the build platform dependency and plugin verifier IDEs. - Add a configuration-time lifecycle log indicating which IDE artifact type was selected.
- Bump
gradle-262.propertiesIDE version from2026.2.0.1to2026.2.1.
Reviewed changes
Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| build.gradle.kts | Switches IntelliJ Platform resolution between ZIP (CI) and installer (local) and logs the chosen artifact; aligns plugin verifier IDE selection with the same rule. |
| gradle-262.properties | Updates the IDE version used for 262 builds to 2026.2.1. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Resolve the IntelliJ Platform IDE per environment: keep the cross-platform (multi-OS) ZIP on CI, but use the complete OS-specific installer for local development so
runIdeworks on recent (2026+) builds. Also bump the 262 target to the released2026.2.1.Background
The build resolves the IntelliJ Platform as the multi-OS ZIP distribution (
useInstaller = false), introduced so CI can cache one OS-agnostic IDE and share it across all runners. That's ideal for headless CI tests, but the ZIP is an incomplete runtime: it bundles no JBR and omits native components — notably JCEF and the 2026 platform-daemon. On 2026+ builds this breaks localrunIde:SEVERE - #c.i.u.j.StartupTest - Startup JCEF test is failed (because CefApp wasn't initialized)NoSuchFileException: .../plugins/platform-daemon-plugin/jetbrainsd_linux_x86_64.tar.gzComparing an installer- vs ZIP-extracted IDE on disk confirmed the root cause: the installer ships a bundled
jbr/and thejetbrainsd_*daemon native; the ZIP ships neither. The JBR is resolved separately by Gradle (the OS-specificcom.jetbrains:jbrartifact, kept in the Gradle cache, not the IDE cache), so it can't backfill the missing native components — only the installer is whole.Changes
useInstaller = !isCIfor both the build platform and the plugin-verifier IDEs, so they stay consistent within each environment.IntelliJ Platform IDE artifact: multi-OS ZIP (CI)/installer (local)), so the selection is visible in build output rather than silent.2026.2.1.Why this is safe on CI
isCIkeys on theCIenvironment variable, which GitHub Actions always sets totrueand no workflow here overrides. CI continues to resolve the ZIP — no change to the IDE caching setup or the workflows.buildPlugin/publishPluginare unaffected.Testing
runIdeverified locally on both 251 and 262 (2026.2.1): JCEF and the platform-daemon start correctly with the installer.installer (local)locally.Note for developers
If you previously ran the ZIP locally, remove the stale ZIP-extracted IDE dir once so the installer re-populates (the managed-cache dir name is identical for both artifacts), e.g.:
Assisted-by: Claude:claude-opus-4-8